docs(ci): point release publish steps at the new /vsce-publish skill#71
Merged
Conversation
The canonical instructions for one-time Azure (aex.dev.azure.com) publisher setup, exact PAT scopes for VSCE_PAT, Open VSX agreement + create-namespace, secret rotation, and troubleshooting now live in the global skill. This makes the workflow self-documenting for future maintainers. Refs #1 Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Point the dual-registry publish steps (VS Code Marketplace + Open VSX) at the newly created global skill.
The skill (
~/.grok/skills/vsce-publish/SKILL.md, invocable as/vsce-publish) now owns the complete knowledge:create-namespace+ Eclipse ownership claim processThis keeps the workflow file short while making the full "everything about vsce setup and publish flow" discoverable and reusable for future extensions.
Refs #1 (umbrella VS Code / IDE extension tracker)
Refs the research on registry permissions for two targets.
Verification
npm run compile && npm run packagegreen